Skip to content

feat: new field ignore_vulnerability_alerts to github_repository#3130

Closed
lens0021 wants to merge 3 commits intointegrations:mainfrom
lens0021:ignore_vulnerability_alerts-to-github_repository
Closed

feat: new field ignore_vulnerability_alerts to github_repository#3130
lens0021 wants to merge 3 commits intointegrations:mainfrom
lens0021:ignore_vulnerability_alerts-to-github_repository

Conversation

@lens0021
Copy link
Copy Markdown

Resolves the second task of #3038


Before the change?

  • ignore_vulnerability_alerts_during_read is only for read, so user cannot control of create, read, or update.

After the change?

  • Setting ignore_vulnerability_alerts to true makes it possible not to call the vulnerability alerts endpoint in any case.

Pull request checklist

  • Schema migrations have been created if needed (example)
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@github-actions
Copy link
Copy Markdown

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

@stevehipwell
Copy link
Copy Markdown
Collaborator

Thanks for the PR @lens0021, but there is a fix on main (#3127) that stops the endpoint being hit on create/update if the field isn't set. This combined with ignore_vulnerability_alerts_during_read already meets the requirements so we don't need another attribute.

@lens0021 lens0021 deleted the ignore_vulnerability_alerts-to-github_repository branch January 28, 2026 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants